This problem i solved.
I have belived that i should use encoders with as high count as possible. I was using ecoders with 41615 counts / inch.
Today i set them down to just over 10160 counts / inch and my machine got much faster and become more stable than ever. Afer ajusting my setup. I went from 0.2 in p to 3.5 now
No more overshooting

--- In DynoMotion@yahoogroups.com, "TK" <tk@...> wrote:
>
> One possibility is that the system is configured to move faster than your
> power supply/amplifiers/motors allow. If the motion trajectory is too fast
> the output will saturate at maximum, the motors will fall behind, and only
> after the trajectory stops will the motors be able to catch up usually with
> a large overshoot.
>
>
>
> Normally this situation would trip an immediate following error fault. But
> possibly you have the Max Following Error set to a very large value.
>
>
>
> If you make a large move using the Step Response Screen you should see all
> this: Output saturates at max, Position falling behind, finally catching up
> and overshooting. Or if something else is happening you should be able to
> see it also.
>
>
>
> First check that your "Max limits - Output" parameter is set to 2047 to
> allow Kanalog to output full +/-10V to the amplifiers.
>
>
>
> G0 and Jog commands are performed as "S" shape (jerk limited) motions
> controlled by the settings in the Step Response Screen in the KMotion.exe
> program. Check that the Max Vel is set reasonably for your system (also
> Accel and Jerk).
>
>
>
> I hope this helps.
>
> TK
>
>
>
> _____
>
> From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On
> Behalf Of s.astrom
> Sent: Saturday, October 17, 2009 2:03 AM
> To: DynoMotion@yahoogroups.com
> Subject: [DynoMotion] Fast movements
>
>
>
>
>
> When i jog or use GO the table does not just make a quick halt when done. It
> moves past the stop point and then reverses i few mm then halts.
> What parameter should i change to correct this?
> This only happens when i use rappid movements
>